fix(examples): redesign vse-gamma-cross as sequencer filmstrips on a grading monitor - #268
Merged
Merged
Conversation
…grading monitor The old hero was a dark board of six small chips with unreadable labels; the key comparison was two near-identical lavender squares, and the chips were emission colors re-encoded through the view transform, not the sequencer's own pixels. The render now shows every frame of the cross, rendered by the VSE and tiled unaltered into two filmstrips: GAMMA_CROSS on top, the sequencer's linear CROSS directly beneath, mounted with closest-texel emission on a hooded grading monitor beside a three-trackball control surface. The endpoints change to orange (1, 0.36, 0) and azure (0, 0.16, 1), whose per-channel square roots sum to 1, so the gamma midpoint is a neutral 0.25 and the dip below the lerp is the per-channel maximum 0.25 (was 0.115) - a dark valley versus violet that reads at card size. The check logic is unchanged; the render path gains the Layer 1 framing gate (exit 10) and a filmstrip guard (exit 9): every frame uniform (5.2 COLOR strips bake scene size at creation, so strips built before the tile resolution letterbox), and each strip's mid frame on its closed form. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]> Signed-off-by: TMHSDigital <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
The gallery review judged the
vse-gamma-crosshero weak: a dark board of six small swatches with tiny unreadable labels, and a key comparison (GAMMA_CROSS t=1/2 vs NAIVE LERP t=1/2) of two near-identical lavender squares that read as nothing at card size. The old chips were also emission colours pushed back through the view transform, so they were not the sequencer's own pixels.This PR is a redesign:
CROSSeffect, frame for frame. Both are mounted with closest-texel emission under the Standard view transform on a hooded grading monitor, beside a three-trackball control surface on a walnut riser. The only authored pixels on the screen are the black surround and three small warm ticks marking the t = 1/2 column. There are no text labels.(1, 0.36, 0)to azure(0, 0.16, 1). Their per-channel square roots sum to 1, so the gamma midpoint is a neutral0.25and the lerp midpoint is violet(0.5, 0.26, 0.5). That is a 0.25 deviation, the per-channel maximum (it was 0.115). At thumbnail size the gamma strip clearly sinks into a dark grey valley while the linear strip passes through violet.Q_TOL,LERP_MID_MIN, exit codes 3 to 7). Only the endpoint constants changed, which makes the witnessed deviation larger.gallery_framing.check_framing(exit 10; the old render path had none) and a filmstrip guard (exit 9). The guard fails if any frame is not uniform, or if either strip's mid frame is off its closed form, so the lower strip really is the lerp.Not an asset-type example (sequencer), so the asset-sheet gate does not apply.
Before / after
docs/gallery/contact-sheets/vse-gamma-cross-contact-sheet.webpdocs/gallery/assets/vse-gamma-cross-hero.webp(24 KB), previewexamples/vse-gamma-cross/preview.webp(22 KB), both written byscripts/render_hero.pyon Blender 5.2.1 LTS.Gate numbers (5.2.1, README
--outputcommand, EEVEE)framing_ok.measure_hero_drift.py --only vse-gamma-cross: mean_abs 0.00338, luma 0.2241/0.2237, matches.Check runs (check-only path)
E:\Blender-Developer-Tools\.scratch\blender-5.2.1-windows-x64\blender.exerun_example.pyPASSE:\Blender-Developer-Tools\.scratch\blender-5.1.2-windows-x64\blender.exerun_example.pyPASSE:\Blender-Developer-Tools\.scratch\blender-4.5.11-windows-x64\blender.exerun_example.pyPASSThe
--outputrender path also ran on all three binaries (EEVEE): exit 0, identical filmstrip guard and framing numbers.Falsifiers (5.2.1)
--swap-inputsGC inputs are not T1 -> T2(f-start)/(duration-1)The probes were temporary copies of the script with a single line replaced; they have been deleted.
Proven by live run
Established by inspection only
🤖 Generated with Claude Code